HAProxy known bugs for maintenance branch 2.8 :  21 

This is maintenance branch 2.8 whose latest version is 2.8.15. If your version is not the last one in the maintenance branch, you are missing fixes for known bugs, and by not updating you are needlessly taking the responsibility for the risk of unexpected service outages and exposing your web site to possible security issues.

The HAProxy development team takes a great care of maintaining stable versions so that all users can apply bug fixes without having to take the risk of upgrading to a new branch. In turn users are expected to apply the fixes when the development team estimates that they were worth being backported to stable branches. In short, if you are running any 2.8 version other than 2.8.15, you're running with known bugs.

Quick links

Versions available in this branch

This branch contains the following releases :

DateVersionComment
2025-04-222.8.15 ⇐ last
2025-01-292.8.14 
2024-12-122.8.13 
2024-11-082.8.12 
2024-09-192.8.11 
2024-06-142.8.10 
2024-04-052.8.9 
2024-04-052.8.8 
2024-02-262.8.7 
2024-02-152.8.6 
2023-12-072.8.5 
2023-11-172.8.4 
2023-09-072.8.3 
2023-08-092.8.2 
2023-07-032.8.1 
2023-05-312.8.0 

Fixes for known bugs pending in this branch since the last release (2.8.15)

These fixes have already been queued for the next 2.8 release but no version was released with them yet. Note that fixes are backported several at a time from the development branch to maintenance branches, and the absence of a fix here doesn't mean none will be issued soon.

Bugs are almost always tagged with a severity (some people forget the severity tag when the bug is minor). The following severities are used :

Total known bugs in the latest version of this branch by category :

TotalCRITICALMAJORMEDIUMMINOR
21 0 1 0 20

Click on the subjects below to get the full description of the bug :

Merge dateSubject - Severity (minor, medium, major, critical)
2025-05-28BUG/MINOR: limits: compute_ideal_maxconn: don't cap remain if fd_hard_limit=0
2025-05-27BUG/MINOR: h3: Set HTX flags corresponding to the scheme found in the request
2025-05-27BUG/MINOR: mux-h2: Reset streams with NO_ERROR code if full response was already sent
2025-05-27BUG/MINOR: h3: don't insert more than one Host header
2025-05-27BUG/MINOR: sink: detect and warn when using "send-proxy" options with ring servers
2025-05-27BUG/MINOR: hlua: Fix Channel:data() and Channel:line() to respect documentation
2025-05-27BUG/MINOR: threads: fix soft-stop without multithreading support
2025-05-27BUG/MINOR: cli: fix too many args detection for commands
2025-05-27BUG/MINOR: quic: reject invalid max_udp_payload size
2025-05-27BUG/MINOR: quic: fix TP reject on invalid max-ack-delay
2025-05-27BUG/MINOR: quic: use proper error code on invalid received TP value
2025-05-27BUG/MINOR: quic: reject retry_source_cid TP on server side
2025-05-27BUG/MINOR: quic: use proper error code on invalid server TP
2025-05-27BUG/MINOR: quic: use proper error code on missing CID in TPs
2025-05-27BUG/MINOR: proxy: only use proxy_inc_fe_cum_sess_ver_ctr() with frontends
2025-05-27BUG/MINOR: mux-h1: Fix trace message in h1_detroy() to not relay on connection
2025-05-27BUG/MINOR: mux-h1: Don't pretend connection was released for TCP>H1>H2 upgrade
2025-05-27BUG/MINOR: dns: prevent ds accumulation within dss
2025-05-27BUG/MINOR: dns: add tempo between 2 connection attempts for dns servers
2025-05-27BUG/MAJOR: listeners: transfer connection accounting when switching listeners
2025-05-27BUG/MINOR: cli: Issue an error when too many args are passed for a command

Known bugs fixed in the development branch after the last commit in this branch

It is important to understand that not all of these commits are necessarily relevant to this version, but clicking on them will show the bug description. All fixes are made first in the development branch and then backported to the maintenance branches. This ensures no fix is lost when upgrading. If a fix was marked for backporting to this branch and is not there yet, it's likely that it is still missing. Do not hesitate to ask on the haproxy mailing list if you feel like a fix has been skipped.

DateSubject
2025-06-03BUG/MAJOR: leastconn: Protect tree_elt with the lbprm lock

Back to the list of branches and versions
Back to the HAProxy page